Communication Method, Communications Apparatus, and Communications System

ABSTRACT

A communication method, a communications apparatus, and a communications system, where the method includes: a first network element receiving identity information of a terminal from a second network element, where the identity information includes an identity of the terminal or an identity of a group of the terminal; the first network element obtaining, based on the identity information, type information of a serving network corresponding to the identity information; and the first network element sending API information of the first network element based on the type information. Based on this method, the second network element can select an available API based on the API information or the type information of the serving network and invoke the available API.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Patent ApplicationNo. PCT/CN2019/078598, filed on Mar. 19, 2019, which claims priority toChinese Patent Application No. 201810313229.9, filed on Apr. 9, 2018.The disclosures of the aforementioned applications are herebyincorporated by reference in their entireties.

TECHNICAL FIELD

This application relates to communications technologies, and inparticular, to a communication method, a communications apparatus, and acommunications system.

BACKGROUND

Explosive development of new services such as Internet of Vehicles,mobile office, and the Internet of Things impose higher requirements oncommunications networks with respect to an access speed, trafficdensity, and other factors. Driven by various types of new services,networks using different access technologies emerge, for example, 4^(th)generation (4G) networks and 5^(th) generation (5G) networks. All of thenetworks using the different access technologies can expose networkfunctions to third-party applications through application programminginterfaces (APIs), and the third-party applications use the APIs toobtain terminal related services.

Because a terminal can support all different access technologies such asa 4G access technology and a 5G access technology, the terminal canflexibly switch between a 4G network and a 5G network. However, when theterminal switches between the 4G network and the 5G network, athird-party application cannot learn the network in which the terminalis currently located, and therefore cannot learn an API that can becurrently invoked. As a result, an API invoke success rate is low, anduser experience is poor.

SUMMARY

This application provides a communication method, a communicationsapparatus, and a communications system, in order to avoid an API invokeerror, ensure an API invoke success rate, and improve user experience.

A first aspect of this application provides a communication method,applied to a first network element, where the method includes:receiving, by the first network element, identity information of aterminal from a second network element, where the identity informationincludes an identity of the terminal or an identity of a group of theterminal; obtaining, by the first network element based on the identityinformation, type information of a serving network corresponding to theidentity information; and sending, by the first network element, APIinformation of the first network element based on the type information.

In this method, after receiving the identity information of the terminalthat is sent by the second network element, the first network elementobtains the type information of the serving network corresponding to theidentity information, and sends the API information or the typeinformation of the serving network to the second network element basedon the type information of the serving network. As such, the secondnetwork element can select an available API based on the API informationor the type information of the serving network and invoke the availableAPI, thereby avoiding an API invoke error, ensuring an API invokesuccess rate, and improving user experience.

In a possible design, the type information includes a type of theserving network or indication information used to indicate that a typeof the serving network changes.

In a possible design, the identity information is included in a firstmessage, and the API information is included in a second message.

In a possible design, the first message is used to subscribe to an APIsupport capability, and the second message is used to notify the APIsupport capability. Alternatively, the first message is used to query anAPI support capability, and the second message is used to respond to thefirst message.

In a possible design, the API information includes API state informationor an API invoke result, and the API state information includes at leastone of the following information: indication information used toindicate that the API support capability changes, a list of availableAPI(s), a list of unavailable API(s), or a list of API state(s), wherethe list of API state(s) includes an identity of an API and a state ofthe API.

In a possible design, the first message is an API support capabilitysubscription message.

In a possible design, the type information is included in the secondmessage, and the second message is used to notify the API supportcapability.

In a possible design, the second message is an API support capabilitynotification message, and the API support capability notificationmessage includes the identity of the terminal or the identity of thegroup.

In a possible design, the first message is a first event subscriptionmessage or a first monitoring request message, and the first eventsubscription message or the first monitoring request message includes anidentity of an API support capability change event.

In a possible design, the second message is a first event notificationmessage or a first monitoring response message, and the first eventnotification message or the first monitoring response message includesthe identity of the terminal or the identity of the group.

In a possible design, the first message is an API support capabilityquery message, and the second message is an API support capabilityresponse message.

In a possible design, the obtaining, by the first network element basedon the identity information, type information of a serving networkcorresponding to the identity information includes: sending, by thefirst network element, a third message to a third network element, wherethe third message is used to request the type information; andreceiving, by the first network element, the type information from thethird network element.

In a possible design, the first message is an API invoke message, andthe API invoke message includes the identity of the terminal or theidentity of the group.

In a possible design, the first message is a second event subscriptionmessage or a second monitoring request message, and the second eventsubscription message or the second monitoring request message includesan identity of a serving network type change event.

In a possible design, the first message is aterminal-register-with-network request message.

In a possible design, the method further includes sending, by the firstnetwork element, the type information.

A second aspect of this application provides a communication method,applied to a second network element, where the method includes: sending,by the second network element, identity information of a terminal to afirst network element, where the identity information includes anidentity of the terminal or an identity of a group of the terminal;receiving, by the second network element, API information of the firstnetwork element from the first network element; and invoking, by thesecond network element, an API based on the API information.

In a possible design, the identity information is included in a firstmessage, and the API information is included in a second message.

In a possible design, the first message is used to subscribe to an APIsupport capability, and the second message is used to notify the APIsupport capability. Alternatively, the first message is used to query anAPI support capability, and the second message is used to respond to thefirst message.

In a possible design, the API information includes API state informationor an API invoke result, and the API state information includes at leastone of the following information: indication information used toindicate that the API support capability changes, a list of availableAPI(s), a list of unavailable API(s), or a list of API state(s), wherethe list of API state(s) includes an identity of an API and a state ofthe API.

In a possible design, the sending, by the second network element,identity information of a terminal to a first network element includes:when the second network element triggers to invoke an API according to aservice requirement, sending the identity information of the terminal tothe first network element; when a preset timer expires, sending theidentity information of the terminal to the first network element; orwhen the second network element receives, from the first networkelement, the indication information used to indicate that the APIsupport capability changes, sending the identity information of theterminal to the first network element.

A third aspect of this application provides a communication method,applied to a first network element, where the method includes: sending,by the first network element, a third message to a third networkelement, where the third message is used to request type information ofa serving network of a terminal or a group of a terminal; receiving, bythe first network element, the type information from the third networkelement; and sending, by the first network element, API information ofthe first network element based on the type information.

In this method, the first network element sends the third message to thethird network element, to request the type information of the servingnetwork of the terminal or the group of the terminal. Additionally, thethird network element obtains, based on the third message, the typeinformation of the serving network of the terminal or the group of theterminal, and sends the type information to the first network element.As such, the first network element can obtain the type information ofthe serving network, and send the API information of the first networkelement or the type information of the serving network to the secondnetwork element, and then the second network element can invoke anavailable API based on the API information or the type information ofthe serving network, thereby avoiding an API invoke error, ensuring anAPI invoke success rate, and improving user experience.

In a possible design, the type information includes a type of theserving network or indication information used to indicate that a typeof the serving network changes.

In a possible design, the type information is included in a fourthmessage.

Additionally, the third message is a subscription message used tosubscribe to the type of the serving network, and the fourth message isa notification message. Alternatively, the third message is a querymessage used to query the type of the serving network, and the fourthmessage is a response message for the third message.

In a possible design, when the third message is used to request the typeinformation of the serving network of the terminal, the third messageincludes an identity of the terminal. Alternatively, when the thirdmessage is used to request the type information of the serving networkof the group of the terminal, the third message includes an identity ofa group of the terminal.

In a possible design, the third message is a third event subscriptionmessage or a third monitoring request message, and the third eventsubscription message or the third monitoring request message includes anidentity of a serving network type change event.

In a possible design, the fourth message is a third event notificationmessage or a third monitoring response message, and the third eventnotification message or the third monitoring response message includes aserving network type change indication or the type of the servingnetwork, and further includes the identity of the terminal or theidentity of the group.

In a possible design, the third message is aterminal-register-with-network request message.

In a possible design, the fourth message is aterminal-register-with-network response message, and theterminal-register-with-network response message includes the type of theserving network, and further includes the identity of the terminal orthe identity of the group.

In a possible design, the API information includes API state informationor an API invoke result, and the API state information includes at leastone of the following information: indication information used toindicate that the API support capability changes, a list of availableAPI(s), a list of unavailable API(s), or a list of API state(s), wherethe list of API state(s) includes an identity of an API and a state ofthe API.

In a possible design, the third network element is a network elementintegrating a home subscriber server (HSS) and uniform data management(UDM); or the third network element is a network element integrating apolicy control function (PCF) and a policy and charging rules function(PCRF); or the third network element is a mobility management entity(MME); or the third network element is an access and mobility managementfunction (AMF).

A fourth aspect of this application provides a communication method,applied to a third network element, where the method includes:receiving, by the third network element, a third message from a firstnetwork element, where the third message is used to request typeinformation of a serving network of a terminal or a group of a terminal;and sending, by the third network element, the type information based onthe third message.

In a possible design, the type information includes a type of theserving network or indication information used to indicate that a typeof the serving network changes.

In a possible design, the type information is included in a fourthmessage.

Additionally, the third message is a subscription message used tosubscribe to the type of the serving network, and the fourth message isa notification message. Alternatively, the third message is a querymessage used to query the type of the serving network, and the fourthmessage is a response message for the third message.

In a possible design, the sending, by the third network element, thetype information based on the third message includes sending, whendetecting that the type of the serving network changes, the informationused to indicate the type of the serving network.

In a possible design, the sending, by the third network element, thetype information based on the third message includes: querying, by thethird network element, the type of the serving network based on thethird message; and sending, by the third network element, the type ofthe serving network.

In a possible design, the third network element is a network elementintegrating a home subscriber server (HSS) and uniform data management(UDM); or the third network element is a network element integrating apolicy control function (PCF) and a policy and charging rules function(PCRF); or the third network element is a mobility management entity(MME); or the third network element is an access and mobility managementfunction (AMF).

In a possible design, when the third message is used to request the typeinformation of the serving network of the terminal, the third messageincludes an identity of the terminal. Alternatively, when the thirdmessage is used to request the type information of the serving networkof the group of the terminal, the third message includes an identity ofa group of the terminal.

A fifth aspect of this application provides a communications apparatus.The communications apparatus is configured to implement functions of thefirst network element in the first aspect. These functions may beimplemented by hardware, or may be implemented by hardware executingcorresponding software. The hardware or software includes one or moremodules corresponding to the foregoing functions.

In a possible design, the communications apparatus may include areceiving module, a processing module, and a sending module. Thereceiving module, the processing module, and the sending module mayperform corresponding functions in the foregoing method. For example,the receiving module is configured to receive identity information of aterminal from a second network element, where the identity informationincludes an identity of the terminal or an identity of a group of theterminal. The processing module is configured to obtain, based on theidentity information, type information of a serving networkcorresponding to the identity information. The sending module isconfigured to send API information of the first network element based onthe type information.

A sixth aspect of this application provides a communications apparatus.The communications apparatus is configured to implement functions of thesecond network element in the second aspect. These functions may beimplemented by hardware, or may be implemented by hardware executingcorresponding software. The hardware or software includes one or moremodules corresponding to the foregoing functions.

In a possible design, the communications apparatus may include areceiving module, a processing module, and a sending module. Thereceiving module, the processing module, and the sending module mayperform corresponding functions in the foregoing method. For example,the sending module is configured to send identity information of aterminal to a first network element, where the identity informationincludes an identity of the terminal or an identity of a group of theterminal. The receiving module is configured to receive, from the firstnetwork element, API information of the first network element. Theprocessing module is configured to invoke an API based on the APIinformation.

A seventh aspect of this application provides a communicationsapparatus. The communications apparatus is configured to implementfunctions of the first network element in the third aspect. Thesefunctions may be implemented by hardware, or may be implemented byhardware executing corresponding software. The hardware or softwareincludes one or more modules corresponding to the foregoing functions.

In a possible design, the communications apparatus may include areceiving module, a processing module, and a sending module. Thereceiving module, the processing module, and the sending module mayperform corresponding functions in the foregoing method. For example,the sending module is configured to send a third message to a thirdnetwork element, where the third message is used to request typeinformation of a serving network of a terminal or a group of a terminal.The receiving module is configured to receive the type information fromthe third network element, and the processing module is configured tosend API information of the first network element based on the typeinformation using the sending module.

An eighth aspect of this application provides a communicationsapparatus. The communications apparatus is configured to implementfunctions of the third network element in the fourth aspect. Thesefunctions may be implemented by hardware, or may be implemented byhardware executing corresponding software. The hardware or softwareincludes one or more modules corresponding to the foregoing functions.

In a possible design, the communications apparatus may include areceiving module, a processing module, and a sending module. Thereceiving module, the processing module, and the sending module mayperform corresponding functions in the foregoing method. For example,the receiving module is configured to receive a third message from afirst network element, where the third message is used to request typeinformation of a serving network of a terminal or a group of a terminal.The processing module is configured to send, based on the third message,the type information using the sending module.

A ninth aspect of this application provides a communications apparatus.The communications apparatus includes a memory and a processor. Thememory is configured to store a program instruction, and the processoris configured to perform the program instruction in the memory, toimplement the method in the first aspect.

A tenth aspect of this application provides a communications apparatus.The communications apparatus includes a memory and a processor. Thememory is configured to store a program instruction, and the processoris configured to perform the program instruction in the memory, toimplement the method in the second aspect.

An eleventh aspect of this application provides a communicationsapparatus. The communications apparatus includes a memory and aprocessor. The memory is configured to store a program instruction, andthe processor is configured to perform the program instruction in thememory, to implement the method in the third aspect.

A twelfth aspect of this application provides a communicationsapparatus. The communications apparatus includes a memory and aprocessor. The memory is configured to store a program instruction, andthe processor is configured to perform the program instruction in thememory, to implement the method in the fourth aspect.

A thirteenth aspect of this application provides a communicationssystem. The communications system includes the communications apparatusaccording to the ninth aspect, the communications apparatus according tothe tenth aspect, the communications apparatus according to the eleventhaspect, and the communications apparatus according to the twelfthaspect.

A fourteenth aspect of this application provides a computer readablestorage medium. The computer storage medium stores a computer program,and the computer program includes instructions used to perform themethod according to the first aspect.

A fifteenth aspect of this application provides a computer readablestorage medium. The computer storage medium stores a computer program,and the computer program includes instructions used to perform themethod according to the second aspect.

A sixteenth aspect of this application provides a computer readablestorage medium. The computer storage medium stores a computer program,and the computer program includes instructions used to perform themethod according to the third aspect.

A seventeenth aspect of this application provides a computer readablestorage medium. The computer storage medium stores a computer program,and the computer program includes instructions used to perform themethod according to the fourth aspect.

An eighteenth aspect of this application provides a computer product.The computer product includes computer program code, and when thecomputer program code is executed, the method according to the firstaspect is performed.

A nineteenth aspect of this application provides a computer product. Thecomputer product includes computer program code, and when the computerprogram code is executed, the method according to the second aspect isperformed.

A twentieth aspect of this application provides a computer product. Thecomputer product includes computer program code, and when the computerprogram code is executed, the method according to the third aspect isperformed.

A twenty-first aspect of this application provides a computer product.The computer product includes computer program code, and when thecomputer program code is executed, the method according to the fourthaspect is performed.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of a network architecture of an evolvedpacket system (EPS);

FIG. 2 is a schematic architectural diagram of a 5G network;

FIG. 3 is a schematic diagram of function support of a capabilityexposure network element;

FIG. 4 is an interaction flowchart of a communication method accordingto this application;

FIG. 5 is an interaction flowchart of another communication methodaccording to this application;

FIG. 6 is a flowchart of a communication method according to Embodiment1;

FIG. 7 is a flowchart of a communication method according to Embodiment2;

FIG. 8 is a flowchart of a communication method according to Embodiment3;

FIG. 9 is a flowchart of a communication method according to Embodiment4;

FIG. 10 is a flowchart of a communication method according to Embodiment5;

FIG. 11 is a flowchart of a communication method according to Embodiment6;

FIG. 12 is a flowchart of a communication method according to Embodiment7;

FIG. 13 is a flowchart of a communication method according to Embodiment8;

FIG. 14 is a flowchart of a communication method according to Embodiment9;

FIG. 15 is a structural diagram of modules in a first communicationsapparatus according to this application;

FIG. 16 is a structural diagram of modules in a second communicationsapparatus according to this application;

FIG. 17 is a structural diagram of modules in a third communicationsapparatus according to this application;

FIG. 18 is a structural diagram of modules in a fourth communicationsapparatus according to this application;

FIG. 19 is a physical block diagram of a first communications apparatusaccording to this application;

FIG. 20 is a physical block diagram of a second communications apparatusaccording to this application;

FIG. 21 is a physical block diagram of a third communications apparatusaccording to this application; and

FIG. 22 is a physical block diagram of a fourth communications apparatusaccording to this application.

DESCRIPTION OF EMBODIMENTS

To make persons skilled in the art better understand the technicalsolutions of this application, the following first describes anarchitecture of a network using different access technologies. AnEvolved Packet System (EPS), namely, a 4G network, and a 5G networkarchitecture are used as an example for description.

FIG. 1 is a schematic diagram of a network architecture of an EPS. Asshown in FIG. 1, the EPS mainly includes network entities such as anEvolved Universal Terrestrial Radio Access Network (EUTRAN), a mobilitymanagement entity (MME), a serving gateway (SGW), a packet data networkgateway (P-GW), a serving General Packet Radio Service (GPRS) supportnode (SGSN), a home subscriber server (HSS), and a policy and chargingrules function (PCRF). Functions of the network entities are as follows.

The EUTRAN is a network including a plurality of evolved NodeBs(eNodeBs), and implements a radio physical layer function, resourcescheduling and radio resource management, radio access control, andmobility management. An eNodeB is connected to the SGW through a userplane interface S1-U, is connected to the MME through a control planeinterface S1-MME, and implements functions such as radio access bearercontrol using an S1-AP protocol.

The MME is mainly responsible for all control plane functions of usersession management, including non-access stratum (NAS) signaling andsecurity, tracking area list management, P-GW and SGW selection, and thelike.

The SGW is mainly responsible for data transmission and forwarding,route switching, and the like of a terminal, and is used as a localmobility anchor when the terminal switches between the eNodeBs (eachterminal is served by only one SGW at a time).

The P-GW is used as an anchor for connecting to a packet data network(PDN), and is responsible for Internet Protocol (IP) address allocation,data packet filtering, rate control, charging information generation,and the like of the terminal.

The SGSN is an access point in a 2^(nd) generation (2G) access network,namely, a Global System for Mobile Communications (GSM) or Enhanced DataRates for GSM Evolution (EDGE) radio access network (GERAN), in a 3^(rd)generation (3G) access network, namely, a universal terrestrial radioaccess network (UTRAN), or in an EPS core network, namely, an evolvedpacket core (EPC), and is responsible for bearer establishment and dataforwarding from the GERAN to the EPC and from the UTRAN to the EPC.

The HSS stores subscription data of a mobile subscriber.

The PCRF is responsible for charging management and policy control,including a policy and charging control (PCC) rule and a quality ofservice (QoS) rule.

A service capability exposure function (SCEF) is responsible forproviding a network function for a third party, for example, receiving aterminal related parameter from a third-party application or subscribingto a terminal related event.

FIG. 2 is a schematic architectural diagram of a 5G network. As shown inFIG. 2, the 5G network includes a terminal, an access network (AN), acore network, and a data network (DN). Functions of the network entitiesare as follows.

The terminal is an ingress for interaction between a mobile subscriberand a network, and is capable of providing a basic computing capabilityand a storage capability, displaying a service window to a user, andreceiving an input operated by a user. The terminal in the 5G networkuses a next generation air interface technology to establish a signalconnection and a data connection to the AN, in order to transmit acontrol signal and service data to a mobile network.

The AN, similar to a base station in a conventional network, is deployedat a position close to the terminal, provides a network access functionfor an authorized user in a specific area, and is capable of using,based on a user level, a service requirement, and the like, transporttunnels of different quality to transmit user data. The AN is capable ofmanaging resources of the AN, using the resources in appropriately,providing an access service for the terminal according to a requirement,and forwarding the control signal and the user data between the terminaland the core network.

The DN is a data network proving a business service for the user.Usually, a client is located in the terminal, and a server is located inthe data network. The data network may be a private network such as alocal area network, may be an external network that is not managed andcontrolled by an operator, such as the Internet, or may be aspecial-purpose network deployed by all operators.

The core network is responsible for maintaining subscription data of themobile network, managing network elements in the mobile network, andproviding functions such as session management, mobility management,policy management, and security authentication for the terminal. Whenthe terminal needs to attach to the core network, the core networkprovides network access authentication for the terminal; when theterminal has a service request, the core network allocates a networkresource to the terminal; when the terminal moves, the core networkupdates a network resource for the terminal; when the terminal is idle,the core network provides a fast recovery mechanism for the terminal;when the network is detached from the core network, the core networkreleases a network resource for the terminal; or when the terminal hasservice data, the core network provides a data routing function for theterminal, for example, forwarding uplink data to the DN; or receivingdownlink data of the terminal from the DN, forwarding the downlink datato the AN, to send the downlink data to the terminal.

The core network may be divided into a user plane and a control plane.The user plane includes a user plane function (UPF), and the controlplane may include an authentication server function (AUSF), an accessand mobility management function (AMF), a session management function(SMF), a network slice selection function (NSSF), a network exposurefunction (NEF), a network function repository function (NRF), unifieddata management (UDM), a policy control function (PCF), an applicationfunction (AF), and the like. Functions of the network entities are asfollows.

The UPF forwards a user data packet according to a routing rule of theSMF.

The AUSF performs security authentication of the terminal.

The AMF performs access management and mobility management of theterminal.

The SMF performs session management of the terminal.

The NSSF selects a network slice for the terminal.

The NEF exposes a network function to a third party through an API.

The NRF stores and selects network function entity information foranother network element.

The UDM performs user subscription context management.

The PCF performs user policy management.

The AF performs user application management.

It can be learned from the network architectures of the 4G network andthe 5G network that the SCEF and the NEF are capability exposure networkelements in the 4G network and the 5G network, respectively, and areresponsible for exposing network functions to a third party.

FIG. 3 is a schematic diagram of function support of a capabilityexposure network element. As shown in FIG. 3, a third-party applicationinteracts with an SCEF through a T8 interface to call an EPS networkservice, and interacts with an NEF through an Nnef interface to call a5G network service. Some of functions supported by the T8 interface andthe Nnef interface are the same, and some of the functions aredifferent. For example, the T8 interface and the Nnef interface cansupport same functions with different interface names, which arereferred to as equivalent functions. For example, a device triggermodule and a trigger service module in FIG. 3 implement same functionsin a 4G network and a 5G network. The T8 interface and the Nnefinterface can also provide feature functions, which are referred to asSCEF feature functions (for example, a numberless short message service(SMS) module implemented only in the 4G network) and NEF featurefunctions (for example, a third-party request module implemented only inthe 5G network). These feature functions are not supported by othersystems.

There are the following problems when network capability exposure isimplemented in an existing network.

When a terminal supports access to both a 4G network and a 5G network,the terminal may switch between the 4G network and the 5G network orregister with the 4G network or the 5G network. It can be learned fromFIG. 3 that when the terminal registers with different networks, thenetworks can expose different capabilities to the terminal. For example,if the terminal currently registers with an EPS network, a third-partyapplication can invoke only APIs related to an equivalent function andan SCEF feature function, and has an error when invoking another API.Alternatively, if the terminal registers with the 5G network, athird-party application can invoke only APIs related to an equivalentfunction and an NEF feature function, and has an error when invokinganother API.

However, in other approaches, when a terminal switches between a 4Gnetwork and a 5G network or registers with the 4G network or the 5Gnetwork, a third-party application cannot learn a network in which theterminal is currently located, and then cannot learn an API that can becurrently invoked. As a result, an API invoke error may be caused.

The technical solutions provided in this application aim to resolve theforegoing problems.

FIG. 4 is an interaction flowchart of a communication method accordingto this application. As shown in FIG. 4, an interaction process of themethod is as follows.

S401. A second network element sends identity information of a terminalto a first network element.

The identity information may include an identity of the terminal or anidentity of a group of the terminal. The identity of the terminal mayidentify the terminal. For example, the identity may be anidentification of the terminal (for example, an international mobilesubscriber identity (IMSI), a general public subscription identifier(GPSI), a mobile subscriber integrated services digital network (ISDN)number (MSISDN), or an External ID). The identity of the group mayidentify a group of the terminal. For example, the identity of the groupmay be a group identification of the terminal (for example, an IMSIGroup ID or an External Group ID).

The group of the terminal may be a group to which the terminal belongsor in which the terminal is located, and the group may include one ormore terminals. The group of the terminal may be determined bysubscription data of the terminal, and may be obtained from thesubscription data of the terminal.

Optionally, the second network element may be an AF (namely, athird-party application), a service capability server (SCS), or anapplication server (AS). The first network element may be a capabilityexposure network element. For example, the first network element may bean SCEF, an NEF, or an SCEF-NEF integrated network element.

The SCEF-NEF integrated network element means that physical deploymentpositions of the SCEF and the NEF are on a same product or server. Aninterface between the SCEF and the NEF is a private interface, andinteraction between the SCEF and the NEF does not need to bestandardized.

Optionally, the second network element sends the identity information ofthe terminal using a first message, and the first message may be used torequest to obtain type information of a serving network corresponding tothe identity information.

In an optional implementation, the first message is a subscriptionmessage. For example, the first message may be used to subscribe to anAPI support capability. After the API support capability is subscribedto using the first message, when the API support capability of the firstnetwork element changes, the first network element may proactivelynotify the second network element that the API support capability of thefirst network element changes.

The API support capability of the first network element is a valid API(or service) provided by the first network element for a specificterminal or a specific group of a terminal. A relationship between the“API” and the “service” is: The “service” is functions that can beprovided by the first network element, and the “API” is a means ofimplementing these functions.

In an example, the first message is an API support capabilitysubscription message, and the API support capability subscriptionmessage includes the identity information of the terminal. Further, theAPI support capability subscription message may include an AF APIcapability, a callback uniform resource identifier (URI), and the like.

The AF API capability is used to indicate an API supported by the AF.The uniform resource identifier is used by the first network element toaddress a callback address. When the API support capability of the firstnetwork element changes, the first network element may proactivelynotify the callback address.

In another example, the first message is a first event subscriptionmessage or a first monitoring request message. The first messageincludes an identity of an API support capability change event and theidentity information of the terminal. The first network element supportsthe API support capability change event, and the API support capabilitychange event may be identified by APISupportCapability Change. Afterreceiving the identity of the API support capability change event, thefirst network element may start to detect the API support capabilitychange event. A process is described in Embodiment 5 below.

Optionally, the first message further includes an AF API capability, acallback URI, and the like.

It should be noted that if the first message includes the callback URI,when sending a second message corresponding to the first message, thefirst network element may send the second message to an addressidentified by the callback URI. In the following embodiments, sameprocessing is performed when the callback URI is used. No description isfurther provided.

In another optional implementation, the first message is a querymessage. For example, the first message is used to query an API supportcapability.

For example, the first message is an API support capability querymessage, and the API support capability query message includes theidentity information of the terminal. Further, the API supportcapability query message may further include an AF API capability.

Optionally, the second network element may perform step S401 in any oneof the following cases, that is, the second network element is triggeredto send the identity information of the terminal to the first networkelement.

Case 1: The second network element triggers to invoke an API accordingto a service requirement.

For example, when invoking an API according to the service requirement,the second network element may send the identity information of theterminal to the first network element before invoking the API, to obtainAPI information of the first network element.

For example, a third network element is an Internet of Vehicles server,and needs to obtain position information of the terminal. In this case,the third network element triggers to invoke a position API, sends theidentity of the terminal to the first network element, and thendetermines, based on the API information returned by the first networkelement, a specific position API to be invoked.

Case 2: A preset timer expires.

Case 3: The second network element receives, from the first networkelement, indication information used to indicate that the API supportcapability changes.

When the second network element receives, from the first networkelement, the indication information used to indicate that the APIsupport capability changes, it indicates that the API support capabilityof the first network element changes. Then, the second network elementmay send the first message to the first network element, to obtain alatest API supported by the first network element.

S402. The first network element obtains, based on the identityinformation of the terminal, type information of a serving networkcorresponding to the identity information.

The serving network may be a network that provides a service for theterminal or the group of the terminal. The serving network may be anetwork with which the terminal or a terminal in the group of theterminal currently registers. For example, for a terminal in a dualregistration mode, two networks simultaneously serve the terminal, andboth the two networks are networks serving the terminal. If someterminals in the group of the terminal register with a network, andother terminals register with another network, both the two networks arenetworks serving the group of the terminal. When all registeredterminals in the group of the terminal register with one network, thenetwork with which the terminals register is the serving network of thegroup of the terminal.

Further, the serving network corresponding to the identity informationmay be a network that provides a service for the terminal or the groupof the terminal that is identified by the identity information.

The type information of the serving network may include a type of theserving network, or indication information used to indicate that a typeof the serving network changes.

For example, the type of the serving network may be a type of a 3^(rd)Generation Partnership Project (3GPP) core network such as an EvolvedPacket Core (EPC) network, a 5G core network (5GC), an EPC/5GC, BOTH, aNon-5GC, 5G, 4G, 3G, or Non-5G, or a combination thereof; or may be a3GPP radio access technology (RAT) such as UTRAN, CDMA2000, GERAN,Long-Term Evolution (LTE), new radio (NR), E-UTRAN, or next generation(NG)-RAN (NG-RAN), or the like. The EPC/5GC means that both the EPC andthe 5GC serve the terminal or the group of the terminal in some cases(for example, in the dual registration mode, or when some terminals inthe group of the terminal are located in the EPC and some terminals arelocated in the 5GC). The indication information used to indicate thatthe type of the serving network changes may be indication informationobtained when the type of the serving network corresponding to theidentity information changes. When obtaining the indication information,the first network element may determine that the type of the servingnetwork corresponding to the identity information changes.

In an implementation, the first network element selects, based on thereceived first message, a corresponding manner to obtain the typeinformation. For example, if the first message is a subscriptionmessage, the first network element subscribes to an event from the thirdnetwork element. Alternatively, if the first message is a query message,the first network element sends a query message to the third networkelement, to query a network type. For a process, refer to the followingembodiments of interactions between the first network element and thethird network element. Details are not described.

S403. The first network element sends API information of the firstnetwork element based on the type information.

Correspondingly, the second network element receives the API informationfrom the first network element.

The API information of the first network element is used to indicate theAPI support capability of the first network element. The second networkelement may determine the API support capability of the first networkelement based on the API information. The API information may be an APIIndication.

For example, when obtaining the type information, the first networkelement may determine the serving network of the terminal or the groupof the terminal that is identified by the identity information, and thefirst network element may further send the API information correspondingto the serving network to the second network element. For example, ifthe terminal is currently located in the EPC network, 4G APIs are usedas available APIs, and the first network element sends information aboutthe available APIs to the second network element. Further, when thefirst message includes the AF API capability, the first network elementselects, from the available APIs based on the AF API capability, an APIsupported by the AF, and sends information about the selected API to thesecond network element.

Optionally, the first network element sends the API information of thefirst network element using the second message. The API information ofthe first network element may be used to indicate an API state of thefirst network element.

In an optional implementation, the API information of the first networkelement may be API state information. The API state information mayinclude at least one of the following information: the indicationinformation used to indicate that the API support capability changes, alist of available API(s), a list of unavailable API(s), or a list of APIstate(s).

The indication information used to indicate that the API supportcapability changes is used to indicate that the API support capabilityof the first network element changes. Further, after receiving theindication information, the second network element may send a requestmessage to the first network element, to obtain change content of theAPI support capability of the first network element.

The list of available API(s) includes an API currently supported by thefirst network element.

The list of unavailable API(s) includes an API currently not supportedby the first network element.

The list of API state(s) includes all APIs of the first network element.For example, the list of API state(s) includes identities of all theAPIs and states corresponding to all the APIs. The state correspondingto an API may be available or unavailable, or may be a suspended stateor a running state, or may be a level of support. An identity of an APIcan identify the API.

For example, a list of API state(s) includes two records: A first recordis an API1 is available; and a second record is an API2 is unavailable.In this case, after receiving the list of API state(s), the secondnetwork element may determine that the API1 can be invoked while theAPI2 cannot be invoked currently.

The suspended state means that a function corresponding to the APIcannot be provided for the terminal, and the running state means that afunction corresponding to the API can be provided normally.

For example, a list of API state(s) includes two records: A first recordis an API1 is in a suspended state; and a second record is an API2 is ina running state. In this case, after receiving the list of API state(s),the second network element may determine that the API2 can be invokedwhile the API1 cannot be invoked currently.

There may be a plurality of levels of support, and one level correspondsto one network type.

For example, it is assumed that a level 1 corresponds to a 5G network,and a level 2 corresponds to a 4G network. If the list of API state(s)includes the level 1, when the second network element invokes an APIfrom the first network element, information about the level 1 iscarried, and the first network element selects an API in a 5G networkfor the second network element based on the level 1.

For example, each API identity in the list of API state(s) correspondsto one API state, and the API state is used to indicate a state of anidentified API. For example, the list of API state(s) includes an APIidentity API1, and an API corresponding to the API1 is in an availablestate. In this case, it indicates that the API identified by the API1 isavailable currently. After receiving the information, the second networkelement may invoke the API1 according to a requirement.

Corresponding to the first message, the second message may be in thefollowing two manners.

Manner 1. When the first message is used to subscribe to the API supportcapability, the second message is used to notify the API supportcapability.

In an example, the second message is an API support capabilitynotification message, and the API support capability notificationmessage includes the API information, and further includes the identityinformation of the terminal.

In another example, the second message is a first event notificationmessage or a first monitoring response message, and the first eventnotification message or the first monitoring response message includesthe identity information of the terminal.

Manner 2. When the first message is used to query the API supportcapability, the second message is used to respond to the first message.

For example, the second message is an API support capability responsemessage, and the API support capability response message includes theAPI information.

In another optional implementation, the API information of the firstnetwork element may be alternatively an API invoke result.

In this implementation, the first message may be an API invoke message,and correspondingly, the second message may be an API invoke responsemessage.

For example, the second network element sends the API invoke message tothe first network element, where the API invoke message is used toinvoke a specific API. After receiving the API invoke message, the firstnetwork element is configured to: obtain the type information of theserving network; determine, based on the type information of the servingnetwork, whether the API that the second network element requests toinvoke is available; and send the second message to the second networkelement, where the second message includes an invoke result of the API.

The API invoke result may be an invoke failure. If the invoke result isan invoke failure, the second message includes an error code. The errorcode may indicate that a cause for the API invoke failure is: A networknever supports the API invoke, or a network does not support the APIinvoke temporarily. If the error code indicates that the network doesnot support the API invoke temporarily, the second message mayadditionally include a timer value, and the second network element mayset a timer based on the timer value, and send the first message againafter the timer expires.

S404. The second network element invokes an API based on the APIinformation.

Optionally, the second network element selects an available API based onthe API information and invokes the selected API.

For example, it is assumed that the API information is the list ofavailable API(s), and the list includes identities of the API1, theAPI2, and an API3. When receiving the API information, the secondnetwork element may learn that the API1, the API2, and the API3 areavailable. Then, the second network element selects the API2 and theAPI3 according to the service requirement and invokes the API2 and theAPI3. Assuming that the API1 is a position API, and an application inthe second network element needs to use the position information of theterminal, the second network element may select the API1 from theavailable API1, API2, and API3, and send an API1 invoke request to thefirst network element. It should be noted that in an alternativeimplementation, the API information sent by the first network element tothe second network element in step S403 may be replaced with the typeinformation of the serving network.

Further, in step S404, the second network element invokes an API basedon the type information of the serving network.

In this implementation, the first message sent by the second networkelement to the first network element in step S401 may be in thefollowing two manners.

Manner 1: Subscription Message

In an example, the first message may be a second event subscriptionmessage or a second monitoring request message. The first messageincludes an identity of a serving network type change event, and furtherincludes the identity information of the terminal. The first networkelement supports the serving network type change event, and the servingnetwork type change event may be identified by CN Type Change. Afterreceiving the identity of the serving network type change event, thefirst network element may start to detect the serving network typechange event. A process is described in Embodiment 8 below.

Optionally, the first message may further include an AF API capability,a callback URI, and the like.

After receiving the first message, the first network element detects theserving network type change event of the terminal. If the event istriggered, the first network element sends the second message. Thesecond message is a second event notification message or a secondmonitoring response message, the second message includes a servingnetwork type change indication or the type of the serving network, andthe second message further includes the identity of the terminal or thegroup of the group. The serving network type change indication may be aCN Type Change Indication.

After receiving the second message, the second network element selectsan available API based on the serving network type change indication orthe type of the serving network and invokes the available API.

For example, if the second message received by the second networkelement includes the serving network type change indication, the secondnetwork element may determine that the serving network of the terminalchanges. Considering that the second network element stores that anetwork in which the terminal is located before the serving networkchanges is the 4G network, the second network element may determine thatthe terminal has switched to the 5G network, and the second networkelement may select and invoke an API in the 5G network.

Manner 2: Query Message

Optionally, the first message may be a terminal-register-with-networkrequest message, and the terminal-register-with-network request messageincludes the identity of the terminal or the identity of the group. Thesecond message is a terminal-register-with-network response message.

After receiving the first message, the first network element queries thethird network element about the type of the serving network.

After obtaining the network type, the first network element sends theterminal-register-with-network response message to the second networkelement, where the terminal-register-with-network response messageincludes the type of the serving network.

Further, the second network element selects the available API based onthe type of the serving network and invokes the available API.

For example, the type of the serving network that is in the secondmessage received by the second network element is an EPC, namely, a 4Gnetwork. In this case, the second network element may select and invokea 4G API.

In this embodiment, after receiving the identity information of theterminal that is sent by the second network element, the first networkelement obtains the type information of the serving networkcorresponding to the identity information, and sends the API informationor the type information of the serving network to the second networkelement based on the type information of the serving network. As such,the second network element can select the available API based on the APIinformation or the type information of the serving network and invokethe available API, thereby avoiding an API invoke error.

FIG. 5 is an interaction flowchart of another communication methodaccording to this application. As shown in FIG. 5, an interactionprocess of the method is as follows.

S501. A first network element sends a third message to a third networkelement, where the third message is used to request type information ofa serving network of a terminal or a group of a terminal.

When the third message is used to request the type information of theserving network of the terminal, the third message may include anidentity of the terminal; or when the third message is used to requestthe type information of the serving network of the group of theterminal, the third message may include an identity of a group of theterminal.

The third network element may be an HSS-UDM integrated network element,a PCF-PCRF integrated network element, an MME, or an AMF. This is notlimited.

In an example, when the third network element is the MME or the AMF, thefirst network element may first send the third message to the HSS-UDMintegrated network element or the PCF-PCRF integrated network element.Then the HSS-UDM integrated network element or the PCF-PCRF integratednetwork element sends the third message to the MME or the AMF.

In another example, when the first network element receives a firstmessage from a second network element, the first network elementperforms this step. To be more specific, when the second network elementrequests to obtain API information of the first network element or thetype information of the serving network of the terminal, the firstnetwork element may send the third message to the third network element,to obtain the type information of the serving network.

For nouns such as the serving network of the terminal or the group ofthe terminal, the type information, the identity of the group, and theidentity of the terminal, refer to the related descriptions in theembodiment shown in FIG. 4. Details are not described herein again.

In an optional implementation, the third message is a subscriptionmessage, and the subscription message is used to subscribe to a type ofthe serving network.

For example, the first message is a third event subscription message ora third monitoring request message. The third event subscription messageor the third monitoring request message includes an identity of aserving network type change event. In addition, the third eventsubscription message or the third monitoring request message furtherincludes the identity of the terminal or the identity of the group. Thethird network element supports the serving network type change event,and the serving network type change event may be identified by CN TypeChange. After receiving the identity of the serving network type changeevent, the third network element may start to detect the serving networktype change event. A process is described in Embodiment 1 below.

In another optional implementation, the third message is a querymessage, and the query message is used to query a type of the servingnetwork.

For example, the third message is a terminal-register-with-networkrequest message, and the terminal-register-with-network request messageincludes the identity of the terminal or the identity of the group.

For example, the third message may be a terminal context requestmessage. For the message, the third network element supports a newcontext type, which is referred to as a serving network type. Theterminal context request message includes a serving network type contexttype identity, the identity of the terminal, or the identity of thegroup.

S502. The third network element sends the type information based on thethird message.

In an example, when the third message is the subscription message, thethird network element may store information about the serving networktype change event in the subscription message, and detect whether thetype of the serving network changes. When detecting that the type of theserving network changes, the third network element sends the typeinformation of the serving network to the first network element.

In another example, when the third message is the query message, thethird network element queries the type of the serving network based onthe third message, and sends the type of the serving network to thefirst network element. The third network element stores a type of anetwork serving the terminal or the group of the terminal. Additionally,after receiving the third message, the third network element recognizesthe identity of the terminal or the identity of the group that is in thethird message, and then queries, from the stored information, a networktype corresponding to the terminal or the group of the terminal.

Optionally, the third network element sends the type information using afourth message.

Corresponding to the third message, the fourth message has the followingtwo forms.

Form 1: When the third message is the subscription message, the fourthmessage is a notification message.

For example, the fourth message is a third event notification message ora third monitoring response message, and the third event notificationmessage or the third monitoring response message includes a servingnetwork type change indication or the type of the serving network, andfurther includes the identity of the terminal or the identity of thegroup. The serving network type change indication may be a CN TypeChange Indication.

Form 2: When the third message is the query message, the fourth messageis a response message for the third message.

For example, the fourth message is a terminal-register-with-networkresponse message, and the terminal-register-with-network responsemessage includes the type information of the serving network.

For example, the fourth message may be a terminal context responsemessage, and the terminal context response message includes the type ofthe serving network.

S503. The first network element sends API information of the firstnetwork element based on the type information.

A process for performing S503 is the same as the process for performingstep S403, and reference may be made to step S403. Details are notdescribed herein again.

In this embodiment, the first network element sends the third message tothe third network element, to request the type information of theserving network of the terminal or the group of the terminal. The thirdnetwork element obtains, based on the third message, the typeinformation of the serving network of the terminal or the group of theterminal, and sends the type information to the first network element.As such, the first network element can obtain the type information ofthe serving network, and send the API information of the first networkelement or the type information of the serving network to the secondnetwork element. Then the second network element can invoke theavailable API based on the API information or the type information ofthe serving network, thereby avoiding an API invoke error.

The following further explains the solutions of this application usingprocess examples. The related embodiments are described below.

Embodiment 1 relates to a communication method between a first networkelement and a third network element. In this method, a subscriptionmessage is used to obtain type information of a serving network of aterminal or a group of a terminal.

Embodiment 2 relates to a communication method between a first networkelement and a third network element. In this method, a subscriptionmessage is used to obtain type information of a serving network of aterminal or a group of a terminal.

Embodiment 3 relates to a communication method between a first networkelement and a third network element. In this method, a query message isused to obtain type information of a serving network of a terminal or agroup of a terminal.

Embodiment 4 relates to a communication method between a first networkelement and a third network element. In this method, a query message isused to obtain type information of a serving network of a terminal or agroup of a terminal.

Embodiment 5 relates to a communication method between a first networkelement and a second network element. In this method, a subscriptionmessage is used, and the first network element returns API stateinformation.

Embodiment 6 relates to a communication method between a first networkelement and a second network element. In this method, a query message isused, and the first network element returns API state information.

Embodiment 7 relates to a communication method between a first networkelement and a second network element. In this method, an API invokemanner is used, and the first network element returns an API invokeresult.

Embodiment 8 relates to a communication method between a first networkelement and a second network element. In this method, a subscriptionmessage is used, and the first network element returns type informationof a serving network.

Embodiment 9 relates to a communication method between a first networkelement and a second network element. In this method, a query message isused, and the first network element returns type information of aserving network.

In the following Embodiments 1 to 9, an SCEF-NEF integrated networkelement is used as an example of the first network element. In addition,in the following embodiments, a message including an identity of aterminal is used as an example. However, a message including an identityof a group of the terminal is also applicable to this application, anddetails are not further described.

Embodiment 1

FIG. 6 is a flowchart of a communication method according toEmbodiment 1. As shown in FIG. 6, a third network element is an HSS-UDMintegrated network element, or a PCF-PCRF integrated network element.The method is described below.

S601. A first network element sends a third event subscription messageto a third network element.

The third event subscription message may include an identity of aserving network type change (CN Type Change) event and an identity of aterminal.

The identity of the CN Type Change event may be an event name or thelike.

After receiving the third event subscription message, the third networkelement may store related information about the CN Type Change event,where the related information about the CN Type Change event includesthe identity of the terminal and the identity of the CN Type Changeevent.

For example, after receiving the third event subscription message, thethird network element stores the identity of the terminal and theidentity of the CN Type Change event that are carried in a thirdmessage.

When the terminal switches between a 4G network and a 5G network orregisters with a 4G network or a 5G network, subsequent steps S604 toS607 are triggered to be performed.

For example, when a position of the terminal changes, the terminal mayswitch between the 4G network and the 5G network, and further,subsequent steps S602 to S605 are triggered to be performed.

S602. An MME sends an update location request message to the thirdnetwork element.

S603. An AMF sends an Nudm_UECM_Registration, Nudm_UECM_Deregistration,Npcf_AMPolicyControl_Get, or Npcf_AMPolicyControl_Delete message to thethird network element.

For example, the Nudm_UECM_Registration message is used to register,with the UDM, information about a network element serving the terminal.The Nudm_UECM_Deregistration message is used to request to delete theinformation about the network element serving the terminal that isstored in the UDM. The Npcf_AMPolicyControl_Get message is used toregister, with the PCF, the information about the network elementserving the network. The Npcf_AMPolicyControl_Delete message is used torequest to delete the information about the network element serving theterminal that is stored in the PCF.

In an example, when the terminal registers with or switches to the 4Gnetwork, the MME may send the Update Location Request message to thethird network element. Additionally, the AMF may send theNudm_UECM_Deregistration message and the Npcf_AMPolicyControl_Deletemessage to the third network element.

In another example, when the terminal registers with or switches to the5G network, the AMF may send the Nudm_UECM_Registration message and theNpcf_AMPolicyControl_Get message to the third network element.

S604. The third network element detects a serving network type changeevent of a terminal.

In an example, when the HSS-UDM integrated network element receives theUpdate Location Request, Nudm_UECM_Registration, orNudm_UECM_Deregistration message, the network element may detect that atype of a serving network changes.

In another example, when the PCF-PCRF integrated network elementreceives the Npcf_AMPolicyControl_Get or Npcf_AMPolicyControl_Deletemessage, the network element may detect that a type of a serving networkchanges.

The Update Location Request, Nudm_UECM_Registration,Nudm_UECM_Deregistration, Npcf_AMPolicyControl_Get, andNpcf_AMPolicyControl_Delete message include the identity of theterminal. Further, the HSS-UDM integrated network element or thePCF-PCRF integrated network element may detect, based on the type of theserving network, a network element identity, the identity of theterminal included in the message, and a sender of the message that arepreviously stored, whether the type of the serving network changes.

For example, before the HSS-UDM integrated network element receives theUpdate Location Request message sent by the MME and theNudm_UECM_Deregistration message sent by the AMF, the type of theserving network of the terminal that is stored by the HSS-UDM integratednetwork element is 5GC, and the network element identity is an AMF nameor an AMF Identifier. Based on the identity of the terminal in thereceived message, the Update Location Request message is sent by theMME, and a network element identity of the AMF that sends theNudm_UECM_Deregistration message is the stored AMF name or AMFIdentifier. In this case, the HSS-UDM integrated network element maydetermine that the type of the serving network changes, and the terminalis currently served by an EPC.

S605. The third network element sends a third event notification messageto the first network element.

The third event notification message includes the identity of theterminal.

In addition, the third event notification message further includes anetwork type change indication (CN Type Change Indication) or the typeof the serving network.

In this embodiment, the first network element sends the third eventsubscription message to the third network element, to request typeinformation of the serving network of the terminal or a group of theterminal. The third network element obtains the type information of theserving network of the terminal or the group of the terminal, and sendsthe type information to the first network element, such that the firstnetwork element can obtain the type information of the serving network,and send API information of the first network element or the typeinformation of the serving network to a second network element. Then thesecond network element can invoke an available API based on the APIinformation or the type information of the serving network, therebyavoiding an API invoke error.

Based on Embodiment 1, this application further provides anothercommunication method. The method includes the foregoing steps S601 toS605, but has the following differences.

The third event subscription message in step S601 is replaced with athird monitoring request message, and the third event notificationmessage in step S605 is replaced with a third monitoring responsemessage. The third monitoring request message may include an identity ofa serving network type change event (CN Type Change) and an identity ofa terminal. The third monitoring response message includes the identityof the terminal and a network type change indication (CN Type ChangeIndication) or the type of the serving network.

Embodiment 2

FIG. 7 is a flowchart of a communication method according to Embodiment2. As shown in FIG. 7, a third network element is an MME or an AMF. Thefollowing steps are described using an example in which the thirdnetwork element is the AMF. Processing related to the MME is describedafter step S705.

S701. A first network element sends a third event subscription messageto an intermediate network element.

The intermediate network element may be an HSS-UDM integrated networkelement, or may be a PCF-PCRF integrated network element. Intermediatenetwork elements in the following embodiments have a same meaning as theintermediate network element herein. Details are not repeated.

The third event subscription message may include an identity of aserving network type change (CN Type Change) event and an identity of aterminal.

The identity of the CN Type Change event may be an event name or thelike.

S702. The intermediate network element sends an event subscriptionmessage to a third network element.

The event subscription message may include the identity of the servingnetwork type change (CN Type Change) event and the identity of theterminal.

It should be noted that this step is an optional step, that is, thefirst network element may send the event subscription message to thethird network element through the intermediate network element.Alternatively, instead of performing this step, the first networkelement directly sends the third event subscription message to the thirdnetwork element.

After receiving the event subscription message sent by the intermediatenetwork element, the third network element may store related informationabout the CN Type Change event, where the related information about theCN Type Change event includes the identity of the terminal and theidentity of the CN Type Change event.

For example, after receiving the event subscription message sent by theintermediate network element, the third network element stores theidentity of the terminal and the identity of the CN Type Change eventthat are carried in the event subscription message.

When the terminal switches between a 4G network and a 5G network orregisters with a 4G network or a 5G network, subsequent steps S703 toS705 are triggered to be performed.

For example, when a position of the terminal changes, the terminal mayswitch between the 4G network and the 5G network, and further,subsequent steps S703 to S705 are triggered to be performed.

S703. The third network element detects a serving network type changeevent of a terminal.

In an example, the third network element is the AMF. When the AMFreceives a switch request from the MME, and the switch request is usedto request to switch the terminal from the 4G network to the 5G network,or when the AMF receives a registration request from the terminal, theAMF determines that a type of a serving network of the terminal changes.

S704. The third network element sends an event notification message tothe intermediate network element.

The event notification message may include the identity of the terminal.In addition, the event notification message may further include aserving network type change indication (CN Type Change Indication) orthe type of the serving network.

S705. The intermediate network element sends a third event notificationmessage to the first network element.

The third event notification message may include the identity of theterminal. In addition, the third event notification message furtherincludes the serving network type change indication (CN Type ChangeIndication) or the type of the serving network.

It should be noted that this step may also be an optional step, that is,the third network element may also directly send the third eventnotification message or a third monitoring response message to the firstnetwork element.

If the third network element is the MME, the first network element sendsthe third monitoring request message to the intermediate network elementin step S701, and the third monitoring request message may include anidentity of the serving network type change (CN Type Change) event andan identity of the terminal. Then, in step S702, the intermediatenetwork element sends a monitoring request message to the third networkelement, and the monitoring request message includes the identity of theserving network type change (CN Type Change) event and the identity ofthe terminal. Then, the third network element stores related informationabout the CN Type Change event. Then, the third network element detectsthe serving network type change event of the terminal. For example,after the MME receives a terminal switch request from the AMF or the MMEreceives an attach request from the terminal, the MME detects that atype of a serving network changes, and then performs subsequent steps.Then, the third network element sends a monitoring response message tothe intermediate network element. The monitoring response message mayinclude the identity of the terminal. In addition, the message furtherincludes a serving network type change indication (CN Type ChangeIndication) or the type of the serving network. Then, the intermediatenetwork element sends a third monitoring response message to the firstnetwork element. The third monitoring response message may include theidentity of the terminal. In addition, the third monitoring responsemessage further includes the serving network type change indication (CNType Change Indication) or the type of the serving network.

It should be noted that a process for performing step S702 may be asfollows.

When the terminal is a terminal in a dual registration mode, theintermediate network element may send the event subscription message toboth the MME and the AMF. When the terminal is not a terminal in a dualregistration mode, if a network element serving the terminal is the MME,the intermediate network element sends the event subscription message tothe MME. If a network element serving the terminal is the AMF, theintermediate network element sends the event subscription message to theAMF.

In this embodiment, the first network element sends the third eventsubscription message or the third monitoring request message to thethird network element, to request type information of the servingnetwork of the terminal or a group of the terminal. The third networkelement obtains the type information of the serving network of theterminal or the group of the terminal, and sends the type information tothe first network element, such that the first network element canobtain the type information of the serving network, and send APIinformation of the first network element or the type information of theserving network to a second network element. Then the second networkelement can invoke an available API based on the API information or thetype information of the serving network, thereby avoiding an API invokeerror.

Embodiment 3

FIG. 8 is an interaction flowchart according to Embodiment 3. As shownin FIG. 8, a third network element is an HSS-UDM integrated networkelement, or a PCF-PCRF integrated network element. A trigger conditionof this embodiment is: A terminal switches between a 4G network and a 5Gnetwork or registers with a 4G network or a 5G network.

The terminal registers with the 4G network or 5G network, or theterminal switches between 4G and 5G, such that an AMF or MME serving theterminal changes, and the following steps S801 to S805 are triggered tobe performed.

For example, when a position of the terminal changes, the terminal mayswitch between the 4G network and the 5G network.

S801. An MME sends an Update Location Request message to a third networkelement.

S802. An AMF sends an Nudm_UECM_Registration, Nudm_UECM_Deregistration,Npcf_AMPolicyControl_Get, or Npcf_AMPolicyControl_Delete message to thethird network element.

For example, the Nudm_UECM_Registration message is used to register,with the UDM, information about a network element serving the terminal.The Nudm_UECM_Deregistration message is used to request to delete theinformation about the network element serving the terminal that isstored in the UDM. The Npcf_AMPolicyControl_Get message is used toregister, with the PCF, the information about the network elementserving the network. The Npcf_AMPolicyControl_Delete message is used torequest to delete the information about the network element serving theterminal that is stored in the PCF.

For example, when the terminal registers with or switches to the 4Gnetwork, the MME may send the Update Location Request message to thethird network element. Additionally, the AMF may send theNudm_UECM_Deregistration message and the Npcf_AMPolicyControl_Deletemessage to the third network element.

When the terminal registers with or switches to the 5G network, the AMFmay send the Nudm_UECM_Registration message and theNpcf_AMPolicyControl_Get message to the third network element.

The third network element stores, based on the received message, anidentity of the network element serving the terminal.

S803. A first network element sends a terminal-register-with-networkrequest message to the third network element, where the message includesan identity of the terminal.

The first network element may periodically send theterminal-register-with-network request message to the third networkelement, or may send the terminal-register-with-network request messageafter receiving a request from an AF.

S804. The third network element determines a type of a serving networkbased on the identity of the terminal in the message.

For example, the third network element determines the type of theserving network based on the stored identity of the network elementserving the terminal.

S805. The third network element sends a terminal-register-with-networkresponse message to the first network element, where the messageincludes the type of the serving network.

In this embodiment, the first network element sends theterminal-register-with-network request message to the third networkelement, to request the type of the serving network of the terminal or agroup of the terminal. The third network element obtains the type of theserving network of the terminal or the group of the terminal, and sendsthe type of the serving network to the first network element, such thatthe first network element can obtain the type of the serving network,and send API information of the first network element or typeinformation of the serving network to a second network element. Then thesecond network element can invoke an available API based on the APIinformation or the type information of the serving network, therebyavoiding an API invoke error.

Embodiment 4

FIG. 9 is an interaction flowchart according to Embodiment 4. As shownin FIG. 9, a third network element is an MME or an AMF. A triggercondition of this embodiment is: A terminal switches between a 4Gnetwork and a 5G network or registers with a 4G network or a 5G network.

For example, the terminal registers with the 4G network or 5G network,or the terminal switches between the 4G network and the 5G network, suchthat the AMF or the MME serving the terminal changes, and the followingsteps S901 to S905 are triggered to be performed.

For example, when a position of the terminal changes, the terminal mayswitch between the 4G network and the 5G network.

S901. A first network element sends a terminal-register-with-networkrequest message to an intermediate network element, where the messageincludes an identity of a terminal.

The first network element may periodically send theterminal-register-with-network request message to the intermediatenetwork element, or may send the terminal-register-with-network requestmessage after receiving a request from an AF.

S902. The intermediate network element sends theterminal-register-with-network request message to a third networkelement.

It should be noted that this step is an optional step, that is, thefirst network element may alternatively directly send theterminal-register-with-network request message to the third networkelement.

S903. The third network element determines a type of a serving networkof the terminal.

For example, if the third network element is the MME, the third networkelement directly determines that the type of the serving network is EPC.If the third network element is the AMF, the third network elementdirectly determines that the type of the serving network is 5GC.

S904. The third network element sends a terminal-register-with-networkresponse message to the intermediate network element.

The terminal-register-with-network response message includes the type ofthe serving network.

S905. The intermediate network element sends theterminal-register-with-network response message to the first networkelement, where the message includes the type of the serving network.

It should be noted that this step is also an optional step, that is, thethird network element may alternatively directly send theterminal-register-with-network response message to the first networkelement.

In this embodiment, the first network element sends theterminal-register-with-network request message to the third networkelement, to request the type of the serving network of the terminal or agroup of the terminal. The third network element obtains the type of theserving network of the terminal or the group of the terminal, and sendsthe type of the serving network to the first network element, such thatthe first network element can obtain the type of the serving network,and send API information of the first network element or typeinformation of the serving network to a second network element. Then thesecond network element can invoke an available API based on the APIinformation or the type information of the serving network, therebyavoiding an API invoke error.

Embodiment 5

FIG. 10 is an interaction flowchart according to Embodiment 5. As shownin FIG. 10, a first network element and a second network elementinteract as follows.

S1001. The second network element sends an API support capabilitysubscription message to the first network element.

The API support capability subscription message may be used to subscribeto an API support capability.

The message includes an identity of a terminal, and reference may bemade to the related descriptions in the foregoing embodiments. Detailsare not further described.

S1002. The first network element detects a serving network type changeevent of a terminal.

Step S1002 may be implemented with reference to the method according toEmbodiment 1 or Embodiment 2. Details are not further described.

S1003. The first network element obtains type information of a servingnetwork, and obtains API information based on the type information.

The API information may be an API Indication. In addition, for theserving network and the type information, refer to the relateddescriptions in the foregoing embodiments. Details are not furtherdescribed.

That the first network element obtains the type information of theserving network in S1003 may be implemented with reference to the methodaccording to Embodiment 1 or 2. Details are not further described.

In an example, when the type of the serving network of the terminalrecorded by the first network element is an EPC, after the first networkelement receives a serving network type change indication sent by athird network element, the first network element determines that theserving network of the terminal changes, and then detects that an APIsupport capability change event occurs. The first network elementgenerates the API information based on the type information, forexample, generates a list of available API(s). Assuming that theterminal moves from a 4G network to a 5G network, after the firstnetwork element detects that the API support capability change eventoccurs, the first network element may determine that an EPC API isunavailable and a 5GC API is available.

S1004. The first network element sends an API support capabilitynotification message to the second network element.

Optionally, the API support capability notification message includes APIstate information and the identity of the terminal.

S1005. The second network element selects an available API based on APIstate information and invokes the available API.

For example, the API state information is the list of available API(s).After receiving the list of available API(s), the second network elementmay select an API in the list of available API(s) and invoke the API.For example, the list of available API(s) includes two records: A firstrecord is an API1, and a second record is an API2. The API1 is aposition API. When an application in the second network element needs touse position information of the terminal, the second network element maysend an API1 invoke request to the first network element.

In this embodiment, after receiving the API support capabilitysubscription message, a first event subscription message, or a firstmonitoring request message that is sent by the second network element,the first network element obtains the type information of the servingnetwork corresponding to the terminal, and sends the API information tothe second network element based on the type information of the servingnetwork. As such, the second network element can select the availableAPI based on the API information and invoke the available API, therebyavoiding an API invoke error.

Based on Embodiment 5, this application further provides anothercommunication method. The method includes the foregoing steps S1001 toS1005, but has the following differences: The API support capabilitysubscription message in step S1001 is replaced with an eventsubscription message, and the API support capability notificationmessage in step S1004 is replaced with an event notification message.

Based on Embodiment 5, this application further provides still anothercommunication method. The method includes the foregoing steps S1001 toS1005, but has the following differences: The API support capabilitysubscription message in step S1001 is replaced with a monitoring requestmessage, and the API support capability notification message in stepS1004 is replaced with a monitoring response message.

The event subscription message or the monitoring request message may beused to subscribe to an API support capability, and the eventsubscription message or the monitoring request message may include anidentity of an API support capability change (APISupportCapabilityChange) event.

Optionally, the event notification message or the monitoring responsemessage includes API state information and an identity of a terminal.

Embodiment 6

FIG. 11 is an interaction flowchart according to Embodiment 6. As shownin FIG. 11, a first network element and a second network elementinteract as follows.

S1101. The second network element sends an API support capability querymessage to the first network element.

The message includes an identity of a terminal.

S1102. The first network element obtains, based on the API supportcapability query message, a type of a serving network of a terminal.

For example, after receiving the API support capability query message,the first network element may send a query message to a third networkelement, to obtain the type of the serving network of the terminal. Fordetails, refer to the methods according to Embodiment 3 and Embodiment4. Details are not further described.

S1103. The first network element determines API information based on thetype of the serving network of the terminal.

For the API information, refer to the related descriptions in theforegoing embodiments. Details are not further described.

For example, when the type of the serving network of the terminal is anEPC, the first network element may determine that an EPC API isavailable and a 5GC API is unavailable, and then generate the APIinformation, for example, a list of available API(s).

S1104. The first network element sends an API support capabilityresponse message to the second network element.

The message includes the API information.

S1105. The second network element selects an available API based on theAPI information and invokes the available API.

For an implementation of step S1105, refer to the related descriptionsin the foregoing embodiments. Details are not further described.

In this embodiment, after receiving the API support capability querymessage sent by the second network element, the first network elementobtains the type information of the serving network corresponding to theterminal, and sends the API information to the second network elementbased on the type information of the serving network. As such, thesecond network element can select the available API based on the APIinformation and invoke the available API, thereby avoiding an API invokeerror.

Embodiment 7

FIG. 12 is an interaction flowchart according to Embodiment 7. As shownin FIG. 12, a first network element and a second network elementinteract as follows.

S1201. The first network element subscribes to a type of a servingnetwork of a terminal from a third network element.

Correspondingly, the third network element may send, to the firstnetwork element, the type of the serving network of the terminal. Forexample, the third network element sends, using a notification messageabout the subscription event, the type of the serving network of theterminal.

S1202. The second network element sends an API invoke request to thefirst network element.

The API invoke request is used to invoke a specific API.

Optionally, when the first network element receives the API invokerequest, and the first network element does not store the type of theserving network of the terminal, step S1203 is performed.

S1203. The first network element obtains, by interacting with the thirdnetwork element, the type of the serving network of the terminal.

Step S1203 may be implemented using the method according to Embodiment 3or 4. Details are not further described.

S1204. The first network element returns an API invoke result to thesecond network element based on the type of the serving network of theterminal.

For example, if the type of the serving network of the terminal is anEPC, and an API that the second network element requests to invoke is a4G API, the first network element normally feeds back an API invokeresponse, to the second network element.

If the type of the serving network of the terminal is an EPC, and an APIthat the second network element requests to invoke is a 5G API, thefirst network element feeds back an API invoke response including anerror code and a timer, to the second network element.

The error code may indicate that the error code is permanently availableor temporarily unavailable. Only when the error code is temporarilyunavailable, the timer is included.

S1205. The second network element determines an invoke manner based onthe API invoke result.

The invoke manner may include: When the timer expires, the API isinvoked again or another API with a similar function as the API isinvoked.

For example, if the first network element normally feeds back the APIinvoke response to the second network element, the second networkelement may continue to perform an API invoke process according to anexisting procedure. If the first network element normally feeds back theAPI invoke response including the error code and the timer, to thesecond network element, after the timer expires, the second networkelement chooses, based on the error code and the timer, to continue toinvoke the original API, or select and invoke another API with a similarfunction as the API.

Embodiment 8

FIG. 13 is an interaction flowchart according to Embodiment 8. As shownin FIG. 13, a first network element and a second network elementinteract as follows.

S1301. The second network element sends a second event subscriptionmessage to the first network element.

The second event subscription message includes an identity of a servingnetwork type change event and an identity of a terminal.

The serving network type change event may be CN Type Change.

S1302. The first network element detects, by interacting with a thirdnetwork element, a serving network type change event of a terminal.

For an example, refer to Embodiment 1 and Embodiment 2.

S1303. The first network element sends a second event notificationmessage to the second network element, where the second eventnotification message includes a serving network type change indicationor a type of a serving network, and further includes an identity of theterminal.

The serving network type change indication may be a CN Type ChangeIndication.

S1304. The second network element selects an available API based on aserving network type change indication or the type of the servingnetwork and invokes the available API.

In this embodiment, after receiving the second event subscriptionmessage or a second monitoring request message that is sent by thesecond network element, the first network element sends the servingnetwork type change indication or the type of the serving network to thesecond network element, such that the second network element can selectthe available API, based on the serving network type change indicationor the type of the serving network and invoke the available API, therebyavoiding an API invoke error.

Based on Embodiment 8, this application further provides anothercommunication method. The method includes the foregoing steps S1301 toS1304, but has the following differences: The second event subscriptionmessage in step S1301 is replaced with a second monitoring requestmessage, and the second event notification message in step S1303 isreplaced with a second monitoring response message.

The second monitoring request message includes an identity of a servingnetwork type change event and an identity of a terminal. The secondmonitoring response message includes a serving network type changeindication or a type of a serving network, and further includes theidentity of the terminal.

Embodiment 9

FIG. 14 is an interaction flowchart according to Embodiment 9. As shownin FIG. 14, a first network element and a second network elementinteract as follows.

S1401. The second network element sends a terminal-register-with-networkrequest message to the first network element, where the message includesan identity of a terminal.

S1402. The second network element obtains, by interacting with a thirdnetwork element, a type of a serving network of the terminal.

S1403. The first network element sends a terminal-register-with-networkresponse message to the second network element, where the messageincludes the type of the serving network of the terminal.

S1404. The second network element selects an available API based on thetype of the serving network of the terminal and invokes the availableAPI.

For example, an AF supports 4G related API functions and 5G related APIfunctions. If the type of the serving network of the terminal that isreceived by the AF is an EPC, the AF determines that a 4G related API isthe available API.

For another example, if the type of the serving network of the terminalthat is received by the AF is an EPC, the AF determines that an APIrelated to an equivalent function or an SCEF feature function is theavailable API.

In this embodiment, after receiving the terminal-register-with-networkrequest message sent by the second network element, the first networkelement sends the type of the serving network to the second networkelement, such that the second network element can select the availableAPI based on the type of the serving network and invoke the availableAPI, thereby avoiding an API invoke error.

It should be pointed out that for the nouns and terms used in theforegoing embodiments, reference may be made to the related descriptionsin the embodiment shown in FIG. 4. Details are not further described.

FIG. 15 is a structural diagram of modules in a first communicationsapparatus according to this application. The apparatus is applied to afirst network element, and is configured to implement functions of thefirst network element in FIG. 4 and FIG. 10 to FIG. 14. As shown in FIG.15, the apparatus includes: a receiving module 1501 configured toreceive identity information of a terminal from a second networkelement, where the identity information includes an identity of theterminal or an identity of a group of the terminal; a processing module1502 configured to obtain, based on the identity information, typeinformation of a serving network corresponding to the identityinformation; and a sending module 1503 configured to send APIinformation of the first network element based on the type information.

Further, the type information includes a type of the serving network orindication information used to indicate that a type of the servingnetwork changes.

Further, the identity information is included in a first message, andthe API information is included in a second message.

Further, the first message is used to subscribe to an API supportcapability, and the second message is used to notify the API supportcapability. Alternatively, the first message is used to query an APIsupport capability, and the second message is used to respond to thefirst message.

Further, the API information includes API state information or an APIinvoke result, and the API state information includes at least one ofthe following information: indication information used to indicate thatthe API support capability changes, a list of available API(s), a listof unavailable API(s), or a list of API state(s), where the list of APIstate(s) includes an identity of an API and a state of the API.

Further, the processing module 1502 is configured to send a thirdmessage to a third network element, where the third message is used torequest the type information; and receive the type information from thethird network element.

FIG. 16 is a structural diagram of modules in a second communicationsapparatus according to this application. The apparatus is applied to asecond network element, and is configured to implement functions of thesecond network element in FIG. 4 and FIG. 10 to FIG. 14. As shown inFIG. 16, the apparatus includes: a sending module 1601 configured tosend identity information of a terminal to a first network element,where the identity information includes an identity of the terminal oran identity of a group of the terminal; a receiving module 1602configured to receive, from the first network element, applicationprogramming interface (API) information of the first network element;and a processing module 1603 configured to invoke an API based on theAPI information.

Further, the identity information is included in a first message, andthe API information is included in a second message.

Further, the first message is used to subscribe to an API supportcapability, and the second message is used to notify the API supportcapability. Alternatively, the first message is used to query an APIsupport capability, and the second message is used to respond to thefirst message.

Further, the API information includes API state information or an APIinvoke result, and the API state information includes at least one ofthe following information: indication information used to indicate thatthe API support capability changes, a list of available API(s), a listof unavailable API(s), or a list of API state(s), where the list of APIstate(s) includes an identity of an API and a state of the API.

Further, the sending module 1601 is configured to: when the secondnetwork element triggers to invoke an API according to a servicerequirement, send the identity information of the terminal to the firstnetwork element; when a preset timer expires, send the identityinformation of the terminal to the first network element; or when thesecond network element receives, from the first network element, theindication information used to indicate that the API support capabilitychanges, send the identity information of the terminal to the firstnetwork element.

Further, the processing module 1603 is configured to: select anavailable API based on the API information; and invoke the selected API.

FIG. 17 is a structural diagram of modules in a third communicationsapparatus according to this application. The apparatus is applied to afirst network element, and is configured to implement functions of thefirst network element in FIG. 5 and FIG. 6 to FIG. 9. As shown in FIG.17, the apparatus includes: a sending module 1701 configured to send athird message to a third network element, where the third message isused to request type information of a serving network of a terminal or agroup of a terminal; a receiving module 1702 configured to receive thetype information from the third network element; and a processing module1703 configured to send API information of the first network elementbased on the type information using the sending module 1701.

Further, the type information includes a type of the serving network orindication information used to indicate that a type of the servingnetwork changes.

Further, the type information is included in a fourth message.Additionally, the third message is a subscription message used tosubscribe to the type of the serving network, and the fourth message isa notification message. Alternatively, the third message is a querymessage used to query the type of the serving network, and the fourthmessage is a response message for the third message.

Further, when the third message is used to request the type informationof the serving network of the terminal, the third message includes anidentity of the terminal. When the third message is used to request thetype information of the serving network of the group of the terminal,the third message includes an identity of a group of the terminal.

Further, the API information includes API state information or an APIinvoke result, and the API state information includes at least one ofthe following information: indication information used to indicate thatthe API support capability changes, a list of available API(s), a listof unavailable API(s), or a list of API state(s), where the list of APIstate(s) includes an identity of an API and a state of the API.

Further, the third network element is an HSS-UDM integrated networkelement; or the third network element is a PCF-PCRF integrated networkelement; or the third network element is an MME; or the third networkelement is an AMF.

FIG. 18 is a structural diagram of modules in a fourth communicationsapparatus according to this application. The apparatus is applied to athird network element, and is configured to implement functions of thethird network element in FIG. 5 and FIG. 6 to FIG. 9. As shown in FIG.18, the apparatus includes a receiving module 1801, a sending module1802, and a processing module 1803.

The receiving module 1801 is configured to receive a third message froma first network element, where the third message is used to request typeinformation of a serving network of a terminal or a group of a terminal.

The processing module 1803 is configured to send the type informationbased on the third message using the sending module 1802.

Further, the type information includes a type of the serving network orindication information used to indicate that a type of the servingnetwork changes.

Further, the type information is included in a fourth message.Additionally, the third message is a subscription message used tosubscribe to the type of the serving network, and the fourth message isa notification message. Alternatively, the third message is a querymessage used to query the type of the serving network, and the fourthmessage is a response message for the third message.

Further, the processing module 1803 is configured such that whendetecting that the type of the serving network changes, processingmodule 1803 sends, using the sending module 1802, the information usedto indicate the type of the serving network.

Further, the processing module 1803 is configured to: query the type ofthe serving network based on the third message; and send the type of theserving network using the sending module 1802.

Further, the third network element is an HSS-UDM integrated networkelement; or the third network element is a PCF-PCRF integrated networkelement; or the third network element is an MME; or the third networkelement is an AMF.

FIG. 19 is a physical block diagram of a first communications apparatus.The apparatus may be the first network element, or an apparatus disposedon the first network element. The first communications apparatus isconfigured to implement functions of the first network element in FIG. 4and FIG. 10 to FIG. 14. As shown in FIG. 19, the apparatus includes amemory and a processor.

The memory 1901 is configured to store a program instruction.

The processor 1902 is configured to execute the program instruction inthe memory 1901 to perform the following method: receiving identityinformation of a terminal from a second network element, where theidentity information includes an identity of the terminal or an identityof a group of the terminal; obtaining, based on the identityinformation, type information of a serving network corresponding to theidentity information; and sending API information of the first networkelement based on the type information.

Further, the type information includes a type of the serving network orindication information used to indicate that a type of the servingnetwork changes.

Further, the identity information is included in a first message, andthe API information is included in a second message.

Further, the first message is used to subscribe to an API supportcapability, and the second message is used to notify the API supportcapability. Alternatively, the first message is used to query an APIsupport capability, and the second message is used to respond to thefirst message.

Further, the API information includes API state information or an APIinvoke result, and the API state information includes at least one ofthe following information: indication information used to indicate thatthe API support capability changes, a list of available API(s), a listof unavailable API(s), or a list of API state(s), where the list of APIstate(s) includes an identity of an API and a state of the API.

Further, the processor 1902 is configured to: send a third message to athird network element, where the third message is used to request thetype information; and receive the type information from the thirdnetwork element.

FIG. 20 is a physical block diagram of a second communicationsapparatus. The apparatus may be the second network element, or anapparatus disposed on the second network element. The secondcommunications apparatus is configured to implement functions of thesecond network element in FIG. 4 and FIG. 10 to FIG. 14. As shown inFIG. 20, the apparatus includes a memory and a processor.

The memory 2001 is configured to store a program instruction.

The processor 2002 is configured to execute the program instruction inthe memory 2001 to perform the following method: sending identityinformation of a terminal to a first network element, where the identityinformation includes an identity of the terminal or an identity of agroup of the terminal; receiving API information of the first networkelement from the first network element; and invoking an API based on theAPI information.

Further, the identity information is included in a first message, andthe API information is included in a second message.

Further, the first message is used to subscribe to an API supportcapability, and the second message is used to notify the API supportcapability. Alternatively, the first message is used to query an APIsupport capability, and the second message is used to respond to thefirst message.

Further, the API information includes API state information or an APIinvoke result, and the API state information includes at least one ofthe following information: indication information used to indicate thatthe API support capability changes, a list of available API(s), a listof unavailable API(s), or a list of API state(s), where the list of APIstate(s) includes an identity of an API and a state of the API.

Further, the processor 2002 is configured to: when the second networkelement triggers to invoke an API according to a service requirement,send the identity information of the terminal to the first networkelement; when a preset timer expires, send the identity information ofthe terminal to the first network element; or when the second networkelement receives, from the first network element, the indicationinformation used to indicate that the API support capability changes,send the identity information of the terminal to the first networkelement.

Further, the processor 2002 is configured to: select an available APIbased on the API information; and invoke the selected API.

FIG. 21 is a physical block diagram of a third communications apparatus.The apparatus may be the first network element, or an apparatus disposedon the first network element. The third communications apparatus isconfigured to implement functions of the first network element in FIG. 5and FIG. 6 to FIG. 9. As shown in FIG. 21, the apparatus includes amemory and a processor.

The memory 2101 is configured to store a program instruction.

The processor 2102 is configured to execute the program instruction inthe memory 2101 to perform the following method: sending a third messageto a third network element, where the third message is used to requesttype information of a serving network of a terminal or a group of aterminal; receiving the type information from the third network element;and sending API information of the first network element based on thetype information.

Further, the type information includes a type of the serving network orindication information used to indicate that a type of the servingnetwork changes.

Further, the type information is included in a fourth message.Additionally, the third message is a subscription message used tosubscribe to the type of the serving network, and the fourth message isa notification message. Alternatively, the third message is a querymessage used to query the type of the serving network, and the fourthmessage is a response message for the third message.

Further, when the third message is used to request the type informationof the serving network of the terminal, the third message includes anidentity of the terminal. When the third message is used to request thetype information of the serving network of the group of the terminal,the third message includes an identity of a group of the terminal.

Further, the API information includes API state information or an APIinvoke result, and the API state information includes at least one ofthe following information: indication information used to indicate thatthe API support capability changes, a list of available API(s), a listof unavailable API(s), or a list of API state(s), where the list of APIstate(s) includes an identity of an API and a state of the API.

Further, the third network element is an HSS-UDM integrated networkelement; or the third network element is a PCF-PCRF integrated networkelement; or the third network element is an MME; or the third networkelement is an AMF.

FIG. 22 is a physical block diagram of a fourth communicationsapparatus. The apparatus may be the third network element, or anapparatus disposed on the third network element. The fourthcommunications apparatus is configured to implement functions of thethird network element in FIG. 5 and FIG. 6 to FIG. 9. As shown in FIG.22, the apparatus includes a memory and a processor.

The memory 2201 is configured to store a program instruction.

The processor 2202 is configured to execute the program instruction inthe memory 2201 to perform the following method: receiving a thirdmessage from a first network element, where the third message is used torequest type information of a serving network of a terminal or a groupof a terminal; and sending the type information based on the thirdmessage.

Further, the type information includes a type of the serving network orindication information used to indicate that a type of the servingnetwork changes.

Further, the type information is included in a fourth message.Additionally, the third message is a subscription message used tosubscribe to the type of the serving network, and the fourth message isa notification message. Alternatively, the third message is a querymessage used to query the type of the serving network, and the fourthmessage is a response message for the third message.

Further, the processor 2202 is configured such that when detecting thatthe type of the serving network changes, the processor 2202 sends theinformation used to indicate the type of the serving network.

Further, the processor 2202 is configured to: query the type of theserving network based on the third message; and send the type of theserving network.

Further, the third network element is an HSS-UDM integrated networkelement; or the third network element is a PCF-PCRF integrated networkelement; or the third network element is an MME; or the third networkelement is an AMF.

This application further provides a communications system. Thecommunications system includes the first communications apparatus, thesecond communications apparatus, the third communications apparatus, andthe fourth communications apparatus in the foregoing.

All or some of the foregoing embodiments may be implemented usingsoftware, hardware, firmware, or any combination thereof. When softwareis used to implement the embodiments, the embodiments may be implementedcompletely or partially in a form of a computer program product. Thecomputer program product includes one or more computer instructions.When the computer program instructions are loaded and executed on acomputer, the procedures or functions according to the embodiments ofthe present application are all or partially generated. The computer maybe a general-purpose computer, a special-purpose computer, a computernetwork, or other programmable apparatuses. The computer instructionsmay be stored in a computer readable storage medium or may betransmitted from a computer readable storage medium to another computerreadable storage medium. For example, the computer instructions may betransmitted from a website, computer, server, or data center to anotherwebsite, computer, server, or data center in a wired (for example,through a coaxial cable, an optical fiber, or a digital subscriber line(DSL)) or wireless (for example, through infrared, radio, or amicrowave) manner. The computer readable storage medium may be anyusable medium accessible to a computer, or a data storage device, suchas a server or a data center, integrating one or more usable media. Theusable medium may be a magnetic medium (for example, a soft disk, a harddisk, or a magnetic tape), an optical medium (for example, a DVD), asemiconductor medium (for example, a solid state disk (SSD)), or thelike.

Persons skilled in the art should understand that the embodiments ofthis application may be provided as a method, a system, or a computerprogram product. Therefore, this application may use a form of hardwareonly embodiments, software only embodiments, or embodiments with acombination of software and hardware. Moreover, this application may usea form of a computer program product that is implemented on one or morecomputer usable storage media (including but not limited to a diskmemory, a compact disk (CD)-read-only memory (CD-ROM), and an opticalmemory) that include computer usable program code.

This application is described with reference to the flowcharts and/orblock diagrams of the method, the apparatus (system), and the computerprogram product according to the embodiments of this application. Itshould be understood that the computer program instructions may be usedto implement each process and/or each block in the flowcharts and/or theblock diagrams, and a combination of a process and/or a block in theflowcharts and/or the block diagrams. These computer programinstructions may be provided for a general-purpose computer, aspecial-purpose computer, an embedded processor, or a processor of anyother programmable data processing device to generate a machine, suchthat the instructions executed by a computer or a processor of any otherprogrammable data processing device generate an apparatus forimplementing a specific function in one or more processes in theflowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions may be stored in a computer readablememory that can instruct the computer or any other programmable dataprocessing device to work in a specific manner, such that theinstructions stored in the computer readable memory generate an artifactthat includes an instruction apparatus. The instruction apparatusimplements a specified function in one or more processes in theflowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions may also be loaded onto a computeror another programmable data processing device, such that a series ofoperations and steps are performed on the computer or the otherprogrammable device, to generate computer-implemented processing.Therefore, the instructions executed on the computer or the otherprogrammable device provide steps for implementing a specific functionin one or more processes in the flowcharts and/or in one or more blocksin the block diagrams.

Although some embodiments of this application have been described,persons skilled in the art can make changes and modifications to theseembodiments once they learn the basic concepts of the disclosure.Therefore, the following claims are intended to be construed as to coverthe embodiments and all changes and modifications falling within thescope of this application.

It should be understood that various modifications and variations tothis application can be made without departing from the spirit and scopeof this application. This application is intended to cover thesemodifications and variations of this application provided that they fallwithin the scope of protection defined by the following claims and theirequivalent technologies.

What is claimed is:
 1. A communications apparatus comprising: anon-transitory memory storage configured to store instructions; and oneor more processors in communication with the non-transitory memorystorage and configured to execute the instructions to: receive identityinformation of a terminal from a second network element, wherein theidentity information comprises a first identity of the terminal or asecond identity of a group of the terminal; obtain, based on theidentity information, type information of a serving networkcorresponding to the identity information; and send, based on the typeinformation, application programming interface (API) information of afirst network element for the terminal or the group.
 2. Thecommunications apparatus according to claim 1, wherein the typeinformation comprises a type of the serving network.
 3. Thecommunications apparatus according to claim 1, wherein the one or moreprocessors are further configured to execute the instructions to:receive a first message from the second network element, wherein thefirst message is for subscribing to an API support capability, andwherein the first message comprises the identity information of theterminal; and send a second message for notifying the API supportcapability, wherein the second message comprises the API information. 4.The communications apparatus according to claim 1, wherein the one ormore processors are further configured to execute the instructions to:receive a first message from the second network element, wherein thefirst message is for querying an API support capability, and wherein thefirst message comprises the identity information of the terminal; andsend a second message for responding to the first message, wherein thesecond message comprises the API information.
 5. The communicationsapparatus according to claim 1, wherein the API information comprisesAPI state information.
 6. The communications apparatus according toclaim 5, wherein the API state information comprises a list of one ormore available APIs.
 7. The communications apparatus according to claim1, wherein the one or more processors are further configured to executethe instructions to: send a third message to a third network element,wherein the third message is for requesting the type information of theserving network; and receive the type information from the third networkelement.
 8. The communications apparatus according to claim 7, whereinthe type information is in a fourth message, wherein the third messageis a subscription message for subscribing to the type information of theserving network, and wherein the fourth message is a notificationmessage.
 9. The communications apparatus according to claim 8, whereinthe subscription message comprises core network (CN) type changeinformation for identifying a serving network type change event.
 10. Thecommunications apparatus according to claim 1, wherein the typeinformation of the serving network is type information of a corenetwork.
 11. The communications apparatus according to claim 10, whereinthe core network comprises an Evolved Packet Core (EPC) network or a5^(th) generation (5G) core network.
 12. A communication system,comprising: a first network element configured to: receive identityinformation of a terminal from a second network element, wherein theidentity information comprises a first identity of the terminal or asecond identity of a group of the terminal; send a third messagerequesting type information of a serving network; receive the typeinformation; and send, based on the type information, applicationprogramming interface (API) information of the first network element forthe terminal or the group; and a third network element configured to:receive the third message from the first network element; and send thetype information to the first network element based on the thirdmessage.
 13. The communication system according to claim 12, wherein thetype information comprises a type of the serving network.
 14. Thecommunication system according to claim 12, wherein the first networkelement is further configured to: receive a first message from thesecond network element, wherein the first message is for subscribing toan API support capability, and wherein the first message comprises theidentity information of the terminal; and send a second message fornotifying the API support capability, wherein the second messagecomprises the API information.
 15. The communication system according toclaim 12, wherein the first network element is further configured to:receive a first message from the second network element, wherein thefirst message is for querying an API support capability, and wherein thefirst message comprises the identity information of the terminal; andsend a second message responding to the first message, wherein thesecond message comprises the API information.
 16. The communicationsystem according to claim 12, wherein the API information comprises APIstate information.
 17. The communication system according to claim 16,wherein the API state information comprises a list of one or moreavailable APIs.
 18. The communication system according to claim 12,wherein the type information is in a fourth message, wherein the thirdmessage is a subscription message for subscribing to the typeinformation of the serving network, and wherein the fourth message is anotification message.
 19. The communication system according to claim18, wherein the subscription message comprises core network (CN) TypeChange identifying a serving network type change event.
 20. Thecommunication system according to claim 12, wherein the type informationof the serving network is type information of a core network.